{2023.06,zen4}[system] EasyBuild v4.9.1 #547
Conversation
|
Instance
|
|
No response from bot on Azure yet 😢 ... checking if it receives an event. |
|
Seems some issue with the bot config file |
|
Fixed issue for both bot: show_config |
Updates by the bot instance
|
Updates by the bot instance
|
|
Instance
|
|
Instance
|
|
bot: build inst:eessi-bot-mc-azure repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
No jobs were submitted ... hmm ... found another glitch in the config. Should be fixed. bot: build inst:eessi-bot-mc-azure repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
Getting closer. However, hit another issue A simple srun --partition x86-64-amd-zen4-node --pty bash
srun: error: Unable to allocate resources: Invalid account or account/partition combination specified |
|
@trz42 Seems fixed after a restart of Slurm service on mgmt node, please try again |
|
bot: build inst:eessi-bot-mc-azure repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
Rebuilding after change which tries to ensure lmod cfg files are created early if they don't exist. bot: build inst:eessi-bot-mc-azure repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
Small mistake (wrong script used) fixed bot: build inst:eessi-bot-mc-azure repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
bot: build inst:eessi-bot-mc-azure repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
bot: build inst:eessi-bot-mc-azure repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
| # stack, we need to ensure certain files are present in | ||
| # ${EESSI_PREFIX}/software/${EESSI_OS_TYPE}/${EESSI_SOFTWARE_SUBDIR_OVERRIDE} | ||
| # - .lmod/lmodrc.lua | ||
| # - .lmod/SitePackage.lua |
There was a problem hiding this comment.
@trz42 Why do these need to be in place exactly?
There was a problem hiding this comment.
It seems these files are needed when init/eessi_environment_variables is sourced. The actual build may still work, but the issue is that the non-existence of these files creates ERROR messages in the slurm output file. The bot/check-build.sh thus considers the job being failed.
There was a problem hiding this comment.
OK, also have to do this here probably means that the same calls at the end of the script are just doing it too late, and it should be moved here (rather than copied)?
I'm happy to merge this as if for now, there's no negative impact when having it on both places, but it's silly, and duplicated code, so we should clean that up afterwards.
There was a problem hiding this comment.
I think we need to have the files created early. As it is now it creates them at the beginning if they don't exist. At the end they are created if they don't exist or if they have changed. So if we check for the change at the beginning we may remove the creation at the end.
| easyconfigs: | ||
| - EasyBuild-4.9.1.eb: | ||
| options: | ||
| from-pr: 20299 |
There was a problem hiding this comment.
Ideally we use --from-commit here, but that's an ongoing discussion in #558, so we can follow it up there, there's some confusion on which commits should be used exactly, so that can be followed-up in there.
boegel
changed the title
|
@trz42 Seems ready to deploy? |
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
rebuilding to pick up fix for |
boegel
added
bot:deploy
Add EasyBuild v4.9.1 to
zen4software subdir.Only build for
zen4on cluster ...SPDX license identifier:
GPL-2.0-onlyMissing packages: